Fix CDS prop nullability if @mandatory
is used
#315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @daogrady 👋 ,
Since the version
8.0.2
, CDS has introduced the new logic for CDS params in CDS functions/actions. Now, we have to use@mandatory
annotation instead of settingnot null
keyword. Whereasnot null
is still working on CDS entity layer..Therefore, I have added a check on
@mandatory
existence in order to determine if the property should/shouldn't be marked as nullable in the compiled TypeScript files.